Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aedc9703250de14aad1cd1b09f33b3bf0620da103fa007f6c4bcb9be3505c920

Tx prefix hash: 74521cf256d362e211b3ab20d9ef760d7b979839f9ed53c9dc02267957c42292
Tx public key: 89143d4a5712d0c452df278509888ed971b4b802638b6ba6cfbb0787f1a3ad2b
Timestamp: 1710389776 Timestamp [UCT]: 2024-03-14 04:16:16 Age [y:d:h:m:s]: 01:033:08:52:40
Block: 977904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284823 RingCT/type: yes/0
Extra: 0189143d4a5712d0c452df278509888ed971b4b802638b6ba6cfbb0787f1a3ad2b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c398be4befc2dcee9fb723e6722c48f0092a3c49fbebbb60023f3a436af00a 0.600000000000 1437911 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": 977914, "vin": [ { "gen": { "height": 977904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c398be4befc2dcee9fb723e6722c48f0092a3c49fbebbb60023f3a436af00a" } } ], "extra": [ 1, 137, 20, 61, 74, 87, 18, 208, 196, 82, 223, 39, 133, 9, 136, 142, 217, 113, 180, 184, 2, 99, 139, 107, 166, 207, 187, 7, 135, 241, 163, 173, 43, 2, 17, 0, 0, 0, 1, 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