Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d6a63f395a0d9083822acaf02ff931e4a755359fd8e416f0a246f30093169f

Tx prefix hash: 3bfcca35a99e5df0fb77353bedc714012011f5e90d9cd7c3ff7f0230c59eba24
Tx public key: 019128923f795498b695edfcfa6c6483d27c46ff55c27751adb56a1d131aeab8
Timestamp: 1662961954 Timestamp [UCT]: 2022-09-12 05:52:34 Age [y:d:h:m:s]: 02:162:16:26:54
Block: 586114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637529 RingCT/type: yes/0
Extra: 01019128923f795498b695edfcfa6c6483d27c46ff55c27751adb56a1d131aeab80211000000026035bcb5000000000000000000

1 output(s) for total of 7.013924551000 dcy

stealth address amount amount idx
00: 3aac3fb87a70638907a89c9ee1d8faefdfe9cb26af276bca48e1ca6b5a6c22a0 7.013924551000 1020176 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": 586124, "vin": [ { "gen": { "height": 586114 } } ], "vout": [ { "amount": 7013924551, "target": { "key": "3aac3fb87a70638907a89c9ee1d8faefdfe9cb26af276bca48e1ca6b5a6c22a0" } } ], "extra": [ 1, 1, 145, 40, 146, 63, 121, 84, 152, 182, 149, 237, 252, 250, 108, 100, 131, 210, 124, 70, 255, 85, 194, 119, 81, 173, 181, 106, 29, 19, 26, 234, 184, 2, 17, 0, 0, 0, 2, 96, 53, 188, 181, 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