Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1a89688067430466cfd780ddd6c9a02b5605ff586a2ce9e5aba0e7fe9753baa

Tx prefix hash: c2d11dc1668f75c6fb7efe82bc2ddd967e3e28b1607f4b85c71787f86b16c050
Tx public key: d0f3acb74cc9ba93156a7f138103e59edb24d9070bef3d5aa1c329dfc363c94d
Timestamp: 1593017501 Timestamp [UCT]: 2020-06-24 16:51:41 Age [y:d:h:m:s]: 04:145:08:26:50
Block: 110432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1044205 RingCT/type: yes/0
Extra: 01d0f3acb74cc9ba93156a7f138103e59edb24d9070bef3d5aa1c329dfc363c94d02110000000546a11e8a000000000000000000

1 output(s) for total of 264.297885687000 dcy

stealth address amount amount idx
00: bc854aa74981bc5640d4daaabb10aa116b5b8d402fe6f1ac3790aa97f7d506f1 264.297885687000 191316 of 0

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": 110442, "vin": [ { "gen": { "height": 110432 } } ], "vout": [ { "amount": 264297885687, "target": { "key": "bc854aa74981bc5640d4daaabb10aa116b5b8d402fe6f1ac3790aa97f7d506f1" } } ], "extra": [ 1, 208, 243, 172, 183, 76, 201, 186, 147, 21, 106, 127, 19, 129, 3, 229, 158, 219, 36, 217, 7, 11, 239, 61, 90, 161, 195, 41, 223, 195, 99, 201, 77, 2, 17, 0, 0, 0, 5, 70, 161, 30, 138, 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