Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3121560d4a223ca11368d3b7aecac5f5dccad04e04f131a1f89b5466ee8ce2d4

Tx prefix hash: e71361995c75dd38e75c02a8de4b01737c4661c3add7200ddaa75d8f128f6332
Tx public key: 8c1c70213eb88d9919a7821e3406631818ba4ddc5c2c6c4cce82d5a7445bb22e
Timestamp: 1724820137 Timestamp [UCT]: 2024-08-28 04:42:17 Age [y:d:h:m:s]: 00:088:17:04:05
Block: 1097506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63452 RingCT/type: yes/0
Extra: 018c1c70213eb88d9919a7821e3406631818ba4ddc5c2c6c4cce82d5a7445bb22e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bce6ef1c148be31db8680fa9f72f2ae31edfb0050d6e172c1c043516e54eeba 0.600000000000 1572903 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": 1097516, "vin": [ { "gen": { "height": 1097506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bce6ef1c148be31db8680fa9f72f2ae31edfb0050d6e172c1c043516e54eeba" } } ], "extra": [ 1, 140, 28, 112, 33, 62, 184, 141, 153, 25, 167, 130, 30, 52, 6, 99, 24, 24, 186, 77, 220, 92, 44, 108, 76, 206, 130, 213, 167, 68, 91, 178, 46, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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