Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed1ebb9a5422464607465b848e1f88291d29a09ce6bc6f04f5c205adf8a4f8d

Tx prefix hash: 55b19db4653937f19ed8b9ab9a76ed0b016062d23793dbe6b2a661b83cd20ced
Tx public key: 690624d33076a41cb00e3dc79c969ab1d8fefeda76c39ad9724cbc3a43091eb6
Timestamp: 1710380597 Timestamp [UCT]: 2024-03-14 01:43:17 Age [y:d:h:m:s]: 00:346:15:20:38
Block: 977826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247807 RingCT/type: yes/0
Extra: 01690624d33076a41cb00e3dc79c969ab1d8fefeda76c39ad9724cbc3a43091eb602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8e0b9fc6cd347a7d4acad703d59f338ed3e7768463d6a0dce4ec433eb2e727e 0.600000000000 1437833 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": 977836, "vin": [ { "gen": { "height": 977826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8e0b9fc6cd347a7d4acad703d59f338ed3e7768463d6a0dce4ec433eb2e727e" } } ], "extra": [ 1, 105, 6, 36, 211, 48, 118, 164, 28, 176, 14, 61, 199, 156, 150, 154, 177, 216, 254, 254, 218, 118, 195, 154, 217, 114, 76, 188, 58, 67, 9, 30, 182, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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