Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83e703e340d6a965058f80beb5e7766a8cae070e70cf353716d63f8c8d55e35b

Tx prefix hash: edea070ec3361364b3773dc50377815e42273374e691c6342c817009ff47b176
Tx public key: 5768be3df1f7f7fc33dfeacd962195f36a192fc4db9d2e192510c272aa353796
Timestamp: 1737312670 Timestamp [UCT]: 2025-01-19 18:51:10 Age [y:d:h:m:s]: 00:252:00:12:12
Block: 1200920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177556 RingCT/type: yes/0
Extra: 015768be3df1f7f7fc33dfeacd962195f36a192fc4db9d2e192510c272aa35379602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66f2e55016a465bce1381ce8687844af0aebf183ba4020ea0e01f8c1742f182e 0.600000000000 1687567 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": 1200930, "vin": [ { "gen": { "height": 1200920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66f2e55016a465bce1381ce8687844af0aebf183ba4020ea0e01f8c1742f182e" } } ], "extra": [ 1, 87, 104, 190, 61, 241, 247, 247, 252, 51, 223, 234, 205, 150, 33, 149, 243, 106, 25, 47, 196, 219, 157, 46, 25, 37, 16, 194, 114, 170, 53, 55, 150, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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