Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e142e2bf26cc8478fe654317425cc344ee2a0ea4a11dcacb6884e8d83fd401

Tx prefix hash: 4aae16ba9a735ff929db261723da4cafdba4d07178822454d3b403aae17178b0
Tx public key: 66a4895d99a0cd47274f1bd5c67ba0f309dcdc399cd4979df253d80f2da63e33
Timestamp: 1722422060 Timestamp [UCT]: 2024-07-31 10:34:20 Age [y:d:h:m:s]: 00:275:22:02:36
Block: 1077632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197126 RingCT/type: yes/0
Extra: 0166a4895d99a0cd47274f1bd5c67ba0f309dcdc399cd4979df253d80f2da63e3302110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354f0b7f49d11272d00226979585b96a4ca000b2bea1c7250e3de24436ebb9c2 0.600000000000 1550187 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": 1077642, "vin": [ { "gen": { "height": 1077632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354f0b7f49d11272d00226979585b96a4ca000b2bea1c7250e3de24436ebb9c2" } } ], "extra": [ 1, 102, 164, 137, 93, 153, 160, 205, 71, 39, 79, 27, 213, 198, 123, 160, 243, 9, 220, 220, 57, 156, 212, 151, 157, 242, 83, 216, 15, 45, 166, 62, 51, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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