Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a416e3fce247d59680900ccd17113e60391afc5da1e177d92624e147926f797

Tx prefix hash: 6bdb3f7722e16a05521a95291984cc5899b4a28716d5440e0225ad7836f56fb4
Tx public key: 2e949ed4bb33cb32bf8f6146999b79566e558032eeb5e881e254a9e9e3d7142c
Timestamp: 1733177730 Timestamp [UCT]: 2024-12-02 22:15:30 Age [y:d:h:m:s]: 00:339:21:20:54
Block: 1166703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240438 RingCT/type: yes/0
Extra: 012e949ed4bb33cb32bf8f6146999b79566e558032eeb5e881e254a9e9e3d7142c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88997660956b8b3153d7aaf5e1aadd53af96f2a904c1f160aa7bdb4e0f2791fa 0.600000000000 1652392 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": 1166713, "vin": [ { "gen": { "height": 1166703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88997660956b8b3153d7aaf5e1aadd53af96f2a904c1f160aa7bdb4e0f2791fa" } } ], "extra": [ 1, 46, 148, 158, 212, 187, 51, 203, 50, 191, 143, 97, 70, 153, 155, 121, 86, 110, 85, 128, 50, 238, 181, 232, 129, 226, 84, 169, 233, 227, 215, 20, 44, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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