Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa239ac2d5afc9205f2d484314ef6581dfc662a72d08f726f1155900760bf873

Tx prefix hash: 17286315539e1352c46f0c8d3eaa323ac6d54873178b058e3780fc05dfb8dc4c
Tx public key: b23ca00a81c2ed94fe436fd84667d9c6e89e0199aeec50151ea6ea5e31483f84
Timestamp: 1706620206 Timestamp [UCT]: 2024-01-30 13:10:06 Age [y:d:h:m:s]: 01:308:13:37:25
Block: 946609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479363 RingCT/type: yes/0
Extra: 01b23ca00a81c2ed94fe436fd84667d9c6e89e0199aeec50151ea6ea5e31483f840211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b506a164a3f891289b0993068aa660875ea1161619edd0df3aee1c20f823bf62 0.600000000000 1404943 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": 946619, "vin": [ { "gen": { "height": 946609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b506a164a3f891289b0993068aa660875ea1161619edd0df3aee1c20f823bf62" } } ], "extra": [ 1, 178, 60, 160, 10, 129, 194, 237, 148, 254, 67, 111, 216, 70, 103, 217, 198, 232, 158, 1, 153, 174, 236, 80, 21, 30, 166, 234, 94, 49, 72, 63, 132, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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