Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b5f5075275ce539d052c8b0fc7b994a0ea7519c76bd6ce0004184e19a2f4d1b8

Tx prefix hash: 94687caeec010211e5f5ceb8bf2bd1107f66084104c9d0c094ae0bafd85536fa
Tx public key: a0018e39b267946ef4b38a8a87a962d5192d3d988b672c78b74205d500b3c46f
Timestamp: 1709272439 Timestamp [UCT]: 2024-03-01 05:53:59 Age [y:d:h:m:s]: 01:036:00:01:07
Block: 968628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286733 RingCT/type: yes/0
Extra: 01a0018e39b267946ef4b38a8a87a962d5192d3d988b672c78b74205d500b3c46f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4564fa437fb6fe2abf98431760ff686a74b6d04199c78382ba210fff1b42e9 0.600000000000 1428445 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 968638, "vin": [ { "gen": { "height": 968628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4564fa437fb6fe2abf98431760ff686a74b6d04199c78382ba210fff1b42e9" } } ], "extra": [ 1, 160, 1, 142, 57, 178, 103, 148, 110, 244, 179, 138, 138, 135, 169, 98, 213, 25, 45, 61, 152, 139, 103, 44, 120, 183, 66, 5, 213, 0, 179, 196, 111, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8