Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7220aa712b16499ad633ecd5b5f8ced59257a912dad68c15ff3623682c402f

Tx prefix hash: cf160fe802311a0bb4386dfd1745b892296675813bf84034813ae6ea369263b2
Tx public key: 5b0265dc00fee89f918e09c5dfc4003328f57261ccfe5690db94ee7adb54c3d0
Timestamp: 1577377029 Timestamp [UCT]: 2019-12-26 16:17:09 Age [y:d:h:m:s]: 05:007:10:35:19
Block: 32307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155272 RingCT/type: yes/0
Extra: 015b0265dc00fee89f918e09c5dfc4003328f57261ccfe5690db94ee7adb54c3d00211000000064943cd9f000000000000000000

1 output(s) for total of 479.683032384000 dcy

stealth address amount amount idx
00: c06ecf641e100c9a5fdf891142b5b7c226bc9ac5eaefe08c0d4b33c0b26fa1bd 479.683032384000 53708 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": 32317, "vin": [ { "gen": { "height": 32307 } } ], "vout": [ { "amount": 479683032384, "target": { "key": "c06ecf641e100c9a5fdf891142b5b7c226bc9ac5eaefe08c0d4b33c0b26fa1bd" } } ], "extra": [ 1, 91, 2, 101, 220, 0, 254, 232, 159, 145, 142, 9, 197, 223, 196, 0, 51, 40, 245, 114, 97, 204, 254, 86, 144, 219, 148, 238, 122, 219, 84, 195, 208, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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