Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa8417083eddf80906b6421acdfe0c5d6623e7f098d26ea9a258115dd8b7130f

Tx prefix hash: 7746c84aa5dce99204aed1a46e47bebef49e377ab4146d6358fe66740b1c0ebe
Tx public key: d96915d4e51c1398eff1c50db96c28d74ce39cea22a231a13da2b4473c9d313f
Timestamp: 1716050282 Timestamp [UCT]: 2024-05-18 16:38:02 Age [y:d:h:m:s]: 00:321:06:49:21
Block: 1024806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229642 RingCT/type: yes/0
Extra: 01d96915d4e51c1398eff1c50db96c28d74ce39cea22a231a13da2b4473c9d313f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b331ba2263ce2b6e1a2946f1cb5c84785fc82aed6b4f53f12bbcb066a94898d0 0.600000000000 1490843 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": 1024816, "vin": [ { "gen": { "height": 1024806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b331ba2263ce2b6e1a2946f1cb5c84785fc82aed6b4f53f12bbcb066a94898d0" } } ], "extra": [ 1, 217, 105, 21, 212, 229, 28, 19, 152, 239, 241, 197, 13, 185, 108, 40, 215, 76, 227, 156, 234, 34, 162, 49, 161, 61, 162, 180, 71, 60, 157, 49, 63, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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