Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6435aae71e0df3f51a46dd573b08915e2fd751e273d47fcf70ee423651dfc07

Tx prefix hash: 79aaa742700d3cc3850d38432321e5c1d84aa78c795a28e7f9f34ff0a54d3927
Tx public key: 62b0f7439c710752a358359674a0c5eefcb2003eec787ea583b9eb29de215285
Timestamp: 1726408410 Timestamp [UCT]: 2024-09-15 13:53:30 Age [y:d:h:m:s]: 01:053:13:35:47
Block: 1110684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296696 RingCT/type: yes/0
Extra: 0162b0f7439c710752a358359674a0c5eefcb2003eec787ea583b9eb29de215285021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5fd6f5e287a66e433652713b30652c4c17d046853b9a667660a6fda065c5f89 0.600000000000 1589375 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": 1110694, "vin": [ { "gen": { "height": 1110684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5fd6f5e287a66e433652713b30652c4c17d046853b9a667660a6fda065c5f89" } } ], "extra": [ 1, 98, 176, 247, 67, 156, 113, 7, 82, 163, 88, 53, 150, 116, 160, 197, 238, 252, 178, 0, 62, 236, 120, 126, 165, 131, 185, 235, 41, 222, 33, 82, 133, 2, 17, 0, 0, 0, 3, 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