Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce1b95fcea0cdc5517c8a6cbe188c44e255fa04d6447c722934e0359f17bb3d

Tx prefix hash: 0b7ca4462631c1f60eb1ec5c7dc60e742e0d9d5a1644dd564e18e0151bc96284
Tx public key: 9fc6eda0a7146ce0b700551e51ce18b93f48c3033e6a0f69256e4cf6185c7b3e
Timestamp: 1697372414 Timestamp [UCT]: 2023-10-15 12:20:14 Age [y:d:h:m:s]: 01:154:19:29:44
Block: 870166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371666 RingCT/type: yes/0
Extra: 019fc6eda0a7146ce0b700551e51ce18b93f48c3033e6a0f69256e4cf6185c7b3e02110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.803117050000 dcy

stealth address amount amount idx
00: ff1dd97b293ec53ab0d89cb84b094bae4ac9d83b65a5d77366d52251118fd827 0.803117050000 1325039 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": 870176, "vin": [ { "gen": { "height": 870166 } } ], "vout": [ { "amount": 803117050, "target": { "key": "ff1dd97b293ec53ab0d89cb84b094bae4ac9d83b65a5d77366d52251118fd827" } } ], "extra": [ 1, 159, 198, 237, 160, 167, 20, 108, 224, 183, 0, 85, 30, 81, 206, 24, 185, 63, 72, 195, 3, 62, 106, 15, 105, 37, 110, 76, 246, 24, 92, 123, 62, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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