Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16fc513e629553b0d86aebfb8f15aaf11eb475f0e85abe466ede4775cba632f6

Tx prefix hash: b00ac5251403d74dfedf5ea889ce1aa576022a34405174450c4fe47bbf65f83a
Tx public key: 3526ff11ffd7ec7744a3087bc8d244850b8172b0df3328f8ce9010c2ae941006
Timestamp: 1701405632 Timestamp [UCT]: 2023-12-01 04:40:32 Age [y:d:h:m:s]: 01:085:04:51:34
Block: 903394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322013 RingCT/type: yes/0
Extra: 013526ff11ffd7ec7744a3087bc8d244850b8172b0df3328f8ce9010c2ae941006021100000004e08532b6000000000000000000

1 output(s) for total of 0.623276338000 dcy

stealth address amount amount idx
00: 3b9b5db438daa34cbf47b78a9603b2cb3f1889ab76306b1156faef5d9a75da7e 0.623276338000 1360073 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": 903404, "vin": [ { "gen": { "height": 903394 } } ], "vout": [ { "amount": 623276338, "target": { "key": "3b9b5db438daa34cbf47b78a9603b2cb3f1889ab76306b1156faef5d9a75da7e" } } ], "extra": [ 1, 53, 38, 255, 17, 255, 215, 236, 119, 68, 163, 8, 123, 200, 210, 68, 133, 11, 129, 114, 176, 223, 51, 40, 248, 206, 144, 16, 194, 174, 148, 16, 6, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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