Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6898af555d7f75d0f9bc37d5f1709ed5e4c411bb972f3fa2cdeb4432bfb961b0

Tx prefix hash: 47ce9c1e34faf166a4e39621c0d5e75318118924fa9de69b2d229df47f6243eb
Tx public key: b2757893e9c90b7c37915ebf9dbfcf6edde4a63d9512332e6de91bd18c9b4616
Timestamp: 1717976725 Timestamp [UCT]: 2024-06-09 23:45:25 Age [y:d:h:m:s]: 01:150:05:20:39
Block: 1040773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365937 RingCT/type: yes/0
Extra: 01b2757893e9c90b7c37915ebf9dbfcf6edde4a63d9512332e6de91bd18c9b46160211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0fa1b8eada888de2dd9062379c2a67d8db141a9e0005a09098f6fd727153380 0.600000000000 1509436 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": 1040783, "vin": [ { "gen": { "height": 1040773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0fa1b8eada888de2dd9062379c2a67d8db141a9e0005a09098f6fd727153380" } } ], "extra": [ 1, 178, 117, 120, 147, 233, 201, 11, 124, 55, 145, 94, 191, 157, 191, 207, 110, 221, 228, 166, 61, 149, 18, 51, 46, 109, 233, 27, 209, 140, 155, 70, 22, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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