Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8234102b17a90398512a8bc8941fc6953d47fad753e7a872b2c4d84ad31372fa

Tx prefix hash: acbdcea80c78cff683bd02562e6b34cf1a76aff3122b578ed3fd8418aaaebf6e
Tx public key: 4b6e45d7f3c02ea3edaf33e9a864d34a5f50acc71c921b72397e8e37eb0722d2
Timestamp: 1704906245 Timestamp [UCT]: 2024-01-10 17:04:05 Age [y:d:h:m:s]: 00:347:13:01:53
Block: 932418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248856 RingCT/type: yes/0
Extra: 014b6e45d7f3c02ea3edaf33e9a864d34a5f50acc71c921b72397e8e37eb0722d202110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cc016a06fc16e6815bc6897d89f16d03c5452da6a16772fcbce91e9d1a6210d 0.600000000000 1390352 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": 932428, "vin": [ { "gen": { "height": 932418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cc016a06fc16e6815bc6897d89f16d03c5452da6a16772fcbce91e9d1a6210d" } } ], "extra": [ 1, 75, 110, 69, 215, 243, 192, 46, 163, 237, 175, 51, 233, 168, 100, 211, 74, 95, 80, 172, 199, 28, 146, 27, 114, 57, 126, 142, 55, 235, 7, 34, 210, 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