Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37453ab3457da393e7ff19f3d75db08f22f0f60e630fdc6626f46da97d917c05

Tx prefix hash: 6310c97772c1c96c4dc703be7067953b0b71d0926ed2e19f82719c6c3e932c23
Tx public key: f9e8b9f88853d97d18087f72c3233b0bcc6cbf679381b383bbfb9607a71667bb
Timestamp: 1723044330 Timestamp [UCT]: 2024-08-07 15:25:30 Age [y:d:h:m:s]: 00:154:05:04:35
Block: 1082788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110334 RingCT/type: yes/0
Extra: 01f9e8b9f88853d97d18087f72c3233b0bcc6cbf679381b383bbfb9607a71667bb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e7cae8ee73b9bbec711ab65349d9a05a3a45585b54570b22e503b6dd0eafbc 0.600000000000 1556619 of 15

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": 1082798, "vin": [ { "gen": { "height": 1082788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e7cae8ee73b9bbec711ab65349d9a05a3a45585b54570b22e503b6dd0eafbc" } } ], "extra": [ 1, 249, 232, 185, 248, 136, 83, 217, 125, 24, 8, 127, 114, 195, 35, 59, 11, 204, 108, 191, 103, 147, 129, 179, 131, 187, 251, 150, 7, 167, 22, 103, 187, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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