Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 957bc25a3e1de48b571ce31f1fca6aa04b14a029f43f5fb66111d4b873d6eb78

Tx prefix hash: f0dd194ccf84a43f279b65c5d84aa1d63ad82a521952d445095094e1cc0e4633
Tx public key: 6a136b94f83a3ca162268d8857fee7315540cb7124e9352c36272eadbcf869be
Timestamp: 1696616312 Timestamp [UCT]: 2023-10-06 18:18:32 Age [y:d:h:m:s]: 01:145:18:42:01
Block: 863898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365194 RingCT/type: yes/0
Extra: 016a136b94f83a3ca162268d8857fee7315540cb7124e9352c36272eadbcf869be021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.842456220000 dcy

stealth address amount amount idx
00: a581143d74961aca4854d21fa964883fd763d0cdca165919d9ee2c3eaf5999e8 0.842456220000 1318394 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": 863908, "vin": [ { "gen": { "height": 863898 } } ], "vout": [ { "amount": 842456220, "target": { "key": "a581143d74961aca4854d21fa964883fd763d0cdca165919d9ee2c3eaf5999e8" } } ], "extra": [ 1, 106, 19, 107, 148, 248, 58, 60, 161, 98, 38, 141, 136, 87, 254, 231, 49, 85, 64, 203, 113, 36, 233, 53, 44, 54, 39, 46, 173, 188, 248, 105, 190, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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