Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae92871a12bab2f89b1506539c754c72da5970dc1c8968e20845c5cd18634ac7

Tx prefix hash: 965e80a96c4ceb2d04450ff6a749828e6a3a3044d8212bfb569065d25a45f293
Tx public key: 52f5c6ef925ea4e42ea8d8d1ef6fb4bb204563b2fddd4ec1a387541ca5037578
Timestamp: 1639300121 Timestamp [UCT]: 2021-12-12 09:08:41 Age [y:d:h:m:s]: 03:324:00:15:07
Block: 393795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008049 RingCT/type: yes/0
Extra: 0152f5c6ef925ea4e42ea8d8d1ef6fb4bb204563b2fddd4ec1a387541ca5037578021100000001408d5ef5000000000000000000

1 output(s) for total of 30.422440714000 dcy

stealth address amount amount idx
00: 91bcf19c4385e329908d200504fd1498d58e6b08e4ba7d8c0b05a7cdec097fb1 30.422440714000 791146 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": 393805, "vin": [ { "gen": { "height": 393795 } } ], "vout": [ { "amount": 30422440714, "target": { "key": "91bcf19c4385e329908d200504fd1498d58e6b08e4ba7d8c0b05a7cdec097fb1" } } ], "extra": [ 1, 82, 245, 198, 239, 146, 94, 164, 228, 46, 168, 216, 209, 239, 111, 180, 187, 32, 69, 99, 178, 253, 221, 78, 193, 163, 135, 84, 28, 165, 3, 117, 120, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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