Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6cde6e9e0dc465323a4417ffc965ad2546e6b52d616428867afb3758e43e76

Tx prefix hash: 861b90851ec4d6447df5d859718910090a37b1b7dde6e37655bfb6d2dcc92a1f
Tx public key: e521d2b666e8e2306a844a2310524870fe20ba97c6af3bae6ac7b9e1a47e8e1f
Timestamp: 1700991376 Timestamp [UCT]: 2023-11-26 09:36:16 Age [y:d:h:m:s]: 01:052:07:18:02
Block: 899959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298774 RingCT/type: yes/0
Extra: 01e521d2b666e8e2306a844a2310524870fe20ba97c6af3bae6ac7b9e1a47e8e1f021100000004faf35c9c000000000000000000

1 output(s) for total of 0.639826503000 dcy

stealth address amount amount idx
00: d804bfe937d440c7b67e280437afd9eff40fe68a6cfc0b40517dc3af6fd917e6 0.639826503000 1356430 of 0

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": 899969, "vin": [ { "gen": { "height": 899959 } } ], "vout": [ { "amount": 639826503, "target": { "key": "d804bfe937d440c7b67e280437afd9eff40fe68a6cfc0b40517dc3af6fd917e6" } } ], "extra": [ 1, 229, 33, 210, 182, 102, 232, 226, 48, 106, 132, 74, 35, 16, 82, 72, 112, 254, 32, 186, 151, 198, 175, 59, 174, 106, 199, 185, 225, 164, 126, 142, 31, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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