Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b806fd4b1993bb3398b9c57f77e235d022d7a9ac14662e04da6aae38ddfe69d

Tx prefix hash: 339a3ea994753be0d26ef4e13386bec76bc23828cfa25950be8281f9bf4dcff4
Tx public key: a8a9e9ea59f002cc7c181647a2ddb6738b441116653d1bf9cf514c2e6a17644b
Timestamp: 1709674206 Timestamp [UCT]: 2024-03-05 21:30:06 Age [y:d:h:m:s]: 01:080:06:04:52
Block: 971955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318396 RingCT/type: yes/0
Extra: 01a8a9e9ea59f002cc7c181647a2ddb6738b441116653d1bf9cf514c2e6a17644b02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5159077f3579b316e74d7ac006534b3aaf4df3eb74957b47e6e1d853d9fd960b 0.600000000000 1431860 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": 971965, "vin": [ { "gen": { "height": 971955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5159077f3579b316e74d7ac006534b3aaf4df3eb74957b47e6e1d853d9fd960b" } } ], "extra": [ 1, 168, 169, 233, 234, 89, 240, 2, 204, 124, 24, 22, 71, 162, 221, 182, 115, 139, 68, 17, 22, 101, 61, 27, 249, 207, 81, 76, 46, 106, 23, 100, 75, 2, 17, 0, 0, 0, 10, 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