Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e356985ddf19f6479516c58d06cbcad8eae8b998f455686de46c0d8a2c42064

Tx prefix hash: 28693693539cd1635b104b66699aed408c1c577ba4a669d949d984a8304b00a9
Tx public key: 5cb5be6840d6c64b4cbc83a6607766e8d2b8d4eebeee8d43fcc0ae649d5f684f
Timestamp: 1711069406 Timestamp [UCT]: 2024-03-22 01:03:26 Age [y:d:h:m:s]: 01:004:02:55:03
Block: 983532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263887 RingCT/type: yes/0
Extra: 015cb5be6840d6c64b4cbc83a6607766e8d2b8d4eebeee8d43fcc0ae649d5f684f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92785ee256f9bb8398bea5fd76540446d87b4597e8b63fd166feb17fb27324d7 0.600000000000 1443673 of 15

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": 983542, "vin": [ { "gen": { "height": 983532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92785ee256f9bb8398bea5fd76540446d87b4597e8b63fd166feb17fb27324d7" } } ], "extra": [ 1, 92, 181, 190, 104, 64, 214, 198, 75, 76, 188, 131, 166, 96, 119, 102, 232, 210, 184, 212, 238, 190, 238, 141, 67, 252, 192, 174, 100, 157, 95, 104, 79, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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