Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d1c6cba175008930474c6fa3b820f6f2954f2bb92ee10fc0852d93e6a9c29a

Tx prefix hash: 53241f3bfdb58748fbce673d429a8ae3bf8e8cfd377bff6e488a94cc357ce86b
Tx public key: 1551957832220e71473219d1a5e90c597a5692bc19b7773aeee5f3ee80fdb2bb
Timestamp: 1649483227 Timestamp [UCT]: 2022-04-09 05:47:07 Age [y:d:h:m:s]: 03:035:15:17:50
Block: 476355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805927 RingCT/type: yes/0
Extra: 011551957832220e71473219d1a5e90c597a5692bc19b7773aeee5f3ee80fdb2bb02110000000ecb8520c2000000000000000000

1 output(s) for total of 16.204602446000 dcy

stealth address amount amount idx
00: fbe7189db06a189021c34e5dc87f0fcb862cca3fa3ae155ebdf17fc3828e6b80 16.204602446000 896798 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": 476365, "vin": [ { "gen": { "height": 476355 } } ], "vout": [ { "amount": 16204602446, "target": { "key": "fbe7189db06a189021c34e5dc87f0fcb862cca3fa3ae155ebdf17fc3828e6b80" } } ], "extra": [ 1, 21, 81, 149, 120, 50, 34, 14, 113, 71, 50, 25, 209, 165, 233, 12, 89, 122, 86, 146, 188, 25, 183, 119, 58, 238, 229, 243, 238, 128, 253, 178, 187, 2, 17, 0, 0, 0, 14, 203, 133, 32, 194, 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