Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73dbe091ee0c9e4742f5d46e8311e03a0b6a158e2c220b236ae3312567fd0231

Tx prefix hash: 9be18545bcc2ba1b87c6793c05588c9cabcd16ad9aa67b2e8900b2f601a38e98
Tx public key: f0238bd3744d35c9c58365fc171613d2804eda5563326e84a8b3751021deaea3
Timestamp: 1639379605 Timestamp [UCT]: 2021-12-13 07:13:25 Age [y:d:h:m:s]: 02:347:08:37:03
Block: 394461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766333 RingCT/type: yes/0
Extra: 01f0238bd3744d35c9c58365fc171613d2804eda5563326e84a8b3751021deaea3021100000002eaa12622000000000000000000

1 output(s) for total of 30.268250393000 dcy

stealth address amount amount idx
00: cde5f579566b3072d11da097ee9f23bd9bc970efdaf7d9fa456057df13e80215 30.268250393000 792056 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": 394471, "vin": [ { "gen": { "height": 394461 } } ], "vout": [ { "amount": 30268250393, "target": { "key": "cde5f579566b3072d11da097ee9f23bd9bc970efdaf7d9fa456057df13e80215" } } ], "extra": [ 1, 240, 35, 139, 211, 116, 77, 53, 201, 197, 131, 101, 252, 23, 22, 19, 210, 128, 78, 218, 85, 99, 50, 110, 132, 168, 179, 117, 16, 33, 222, 174, 163, 2, 17, 0, 0, 0, 2, 234, 161, 38, 34, 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