Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0804bbcd7d00fe9081ce0bc3b150fb59b6dde57d442972fdc13993a1177119c2

Tx prefix hash: a6185f1c644e4a0f413af00cc65a3386152ccce06c56213a9a012cad6a0a53a2
Tx public key: aae863b3716c5731f8887ef3af3ef3ad8f0f9c8c1756ec6f2c2385a67092bdfc
Timestamp: 1706700656 Timestamp [UCT]: 2024-01-31 11:30:56 Age [y:d:h:m:s]: 01:281:21:12:04
Block: 947278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460262 RingCT/type: yes/0
Extra: 01aae863b3716c5731f8887ef3af3ef3ad8f0f9c8c1756ec6f2c2385a67092bdfc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d344260b8c69ee39bc41a8d38e3f25a1874c7425f5322c9f2e3b1c18a39949a 0.600000000000 1405626 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": 947288, "vin": [ { "gen": { "height": 947278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d344260b8c69ee39bc41a8d38e3f25a1874c7425f5322c9f2e3b1c18a39949a" } } ], "extra": [ 1, 170, 232, 99, 179, 113, 108, 87, 49, 248, 136, 126, 243, 175, 62, 243, 173, 143, 15, 156, 140, 23, 86, 236, 111, 44, 35, 133, 166, 112, 146, 189, 252, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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