Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3f9ffb55e4e4d5d68184d4b2b4e8032569d100144214be93e1dbffbebf66e2

Tx prefix hash: facfc1d7a4e56dc595d58c60fa152a6143c23934b9a408962bbbed82d5a8f8e5
Tx public key: c11a96d36fef475d1a033b4f9b3511409ae1fa82693f2c8d4ef22817a5e1891a
Timestamp: 1727154724 Timestamp [UCT]: 2024-09-24 05:12:04 Age [y:d:h:m:s]: 00:121:04:15:30
Block: 1116873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86599 RingCT/type: yes/0
Extra: 01c11a96d36fef475d1a033b4f9b3511409ae1fa82693f2c8d4ef22817a5e1891a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d94331be9f718343ae66e88ad84a2519ebcdfd8e68200842474692f112cff2e 0.600000000000 1597508 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": 1116883, "vin": [ { "gen": { "height": 1116873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d94331be9f718343ae66e88ad84a2519ebcdfd8e68200842474692f112cff2e" } } ], "extra": [ 1, 193, 26, 150, 211, 111, 239, 71, 93, 26, 3, 59, 79, 155, 53, 17, 64, 154, 225, 250, 130, 105, 63, 44, 141, 78, 242, 40, 23, 165, 225, 137, 26, 2, 17, 0, 0, 0, 8, 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