Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add41edc8caf69f6df2302cb1e6f70ac462906679e99ff70ac0d70341093a87c

Tx prefix hash: 0421d39e3bbd384c9657e4aa1b62cf86323cc9725655686772c054a3a0edcdac
Tx public key: 73068d7dc7d1af7bb3779de228cc8ed3911dd9d1c8a6e5a65928c42015d9019e
Timestamp: 1722859499 Timestamp [UCT]: 2024-08-05 12:04:59 Age [y:d:h:m:s]: 01:094:01:40:03
Block: 1081261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325704 RingCT/type: yes/0
Extra: 0173068d7dc7d1af7bb3779de228cc8ed3911dd9d1c8a6e5a65928c42015d9019e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc9aac96b1903a61e534304bdadd12fdda9ae56c23d557afb73d7cea027797b 0.600000000000 1554940 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": 1081271, "vin": [ { "gen": { "height": 1081261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc9aac96b1903a61e534304bdadd12fdda9ae56c23d557afb73d7cea027797b" } } ], "extra": [ 1, 115, 6, 141, 125, 199, 209, 175, 123, 179, 119, 157, 226, 40, 204, 142, 211, 145, 29, 217, 209, 200, 166, 229, 166, 89, 40, 196, 32, 21, 217, 1, 158, 2, 17, 0, 0, 0, 5, 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