Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b26aa2e870edc554361f92a9111c62a78641e2996d038d364dfafd7799d56d

Tx prefix hash: 054a88c8ec00e0126832f517771c2cba733fcc70ba38738316e3d690f04b172e
Tx public key: c68f3ecbb8b788f2427f872b660239a9e936d7cb2a6030ce735775a8f4800fd1
Timestamp: 1703871613 Timestamp [UCT]: 2023-12-29 17:40:13 Age [y:d:h:m:s]: 01:358:23:49:40
Block: 923839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515455 RingCT/type: yes/0
Extra: 01c68f3ecbb8b788f2427f872b660239a9e936d7cb2a6030ce735775a8f4800fd10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 315c144709d0acfdeee4904ad8712bceb115d59914b1aab4f8a67ad2c216f3e4 0.600000000000 1381577 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": 923849, "vin": [ { "gen": { "height": 923839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "315c144709d0acfdeee4904ad8712bceb115d59914b1aab4f8a67ad2c216f3e4" } } ], "extra": [ 1, 198, 143, 62, 203, 184, 183, 136, 242, 66, 127, 135, 43, 102, 2, 57, 169, 233, 54, 215, 203, 42, 96, 48, 206, 115, 87, 117, 168, 244, 128, 15, 209, 2, 17, 0, 0, 0, 5, 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