Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321178f91603f524519a63653304593de019169e423e7c4ce1c44f1619c4887b

Tx prefix hash: bbc97f47a6e600f05cdac2c26a0f4abf416e4ae48e1a1282187621c8e130514c
Tx public key: 229d6188330b0201b8bfa57bf601552d32876b439d438af97617f8b07e4a72b4
Timestamp: 1577687346 Timestamp [UCT]: 2019-12-30 06:29:06 Age [y:d:h:m:s]: 05:065:16:25:38
Block: 34825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196723 RingCT/type: yes/0
Extra: 01229d6188330b0201b8bfa57bf601552d32876b439d438af97617f8b07e4a72b40211000000018a2ee0d9000000000000000000

1 output(s) for total of 470.555846412000 dcy

stealth address amount amount idx
00: 1d0508f35f95d42598ec578e634b4f6c3c79b01b70ca91d946719a936ac891e5 470.555846412000 58666 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": 34835, "vin": [ { "gen": { "height": 34825 } } ], "vout": [ { "amount": 470555846412, "target": { "key": "1d0508f35f95d42598ec578e634b4f6c3c79b01b70ca91d946719a936ac891e5" } } ], "extra": [ 1, 34, 157, 97, 136, 51, 11, 2, 1, 184, 191, 165, 123, 246, 1, 85, 45, 50, 135, 107, 67, 157, 67, 138, 249, 118, 23, 248, 176, 126, 74, 114, 180, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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