Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd56966757eb4062e3fc206900cf3ddfc5ce74e19d1e37f2e24b07f9364a99ab

Tx prefix hash: 1033cb0452d4586dee697bf8bab11bb0a5069c33950271b69469cb0354b41a1e
Tx public key: 988b16c1b3e0d48fc9f5297b84a15dcec5247b47c6fd4f8eaeb7104c7f0d07a9
Timestamp: 1732896270 Timestamp [UCT]: 2024-11-29 16:04:30 Age [y:d:h:m:s]: 00:115:17:41:42
Block: 1164373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82514 RingCT/type: yes/0
Extra: 01988b16c1b3e0d48fc9f5297b84a15dcec5247b47c6fd4f8eaeb7104c7f0d07a9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb0068a6a324f039c149ba7f7d367ae3fb1b60c86e92bfcfac75be1d8ff957e9 0.600000000000 1650046 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": 1164383, "vin": [ { "gen": { "height": 1164373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb0068a6a324f039c149ba7f7d367ae3fb1b60c86e92bfcfac75be1d8ff957e9" } } ], "extra": [ 1, 152, 139, 22, 193, 179, 224, 212, 143, 201, 245, 41, 123, 132, 161, 93, 206, 197, 36, 123, 71, 198, 253, 79, 142, 174, 183, 16, 76, 127, 13, 7, 169, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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