Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d1a1b05d876fb42ef20d84db1e9c7c8cd63d5c1849e38c5b7403dcaf415aaaa

Tx prefix hash: 17a7647dcd2008434aeea3d89d51f8608a4d953bd1ab23a7f4a7a156d305f75f
Tx public key: 0e1224e8e751b3408a16305812447e0e74575b3d3778850a1e08c471da8988d2
Timestamp: 1577881567 Timestamp [UCT]: 2020-01-01 12:26:07 Age [y:d:h:m:s]: 05:033:22:12:45
Block: 36332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174103 RingCT/type: yes/0
Extra: 010e1224e8e751b3408a16305812447e0e74575b3d3778850a1e08c471da8988d2021100000053d81c26c0000000000000000000

1 output(s) for total of 465.184634423000 dcy

stealth address amount amount idx
00: 11d0ab1165f69bf0c9209794727de977705f3d0095ed163af5999086644b9cc9 465.184634423000 61517 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": 36342, "vin": [ { "gen": { "height": 36332 } } ], "vout": [ { "amount": 465184634423, "target": { "key": "11d0ab1165f69bf0c9209794727de977705f3d0095ed163af5999086644b9cc9" } } ], "extra": [ 1, 14, 18, 36, 232, 231, 81, 179, 64, 138, 22, 48, 88, 18, 68, 126, 14, 116, 87, 91, 61, 55, 120, 133, 10, 30, 8, 196, 113, 218, 137, 136, 210, 2, 17, 0, 0, 0, 83, 216, 28, 38, 192, 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