Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea72e6f257dfe4c281382f38ab4e2b49af354f5283b81ab1b73433e4182790c

Tx prefix hash: 48712bfcd121f0a35222b95bbdd719ee09341d903d87fd70faa3db92d17c0883
Tx public key: b34a8755832fd292bf3efd45dfde2baa87d818184a1ad326fe8aefd02d005d54
Timestamp: 1706776853 Timestamp [UCT]: 2024-02-01 08:40:53 Age [y:d:h:m:s]: 01:068:03:16:24
Block: 947906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309782 RingCT/type: yes/0
Extra: 01b34a8755832fd292bf3efd45dfde2baa87d818184a1ad326fe8aefd02d005d540211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e660dc0fc59ff18af3d27aa6c909e56f22824afca7fc86d5f9c0b62cec66bfc 0.600000000000 1406266 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": 947916, "vin": [ { "gen": { "height": 947906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e660dc0fc59ff18af3d27aa6c909e56f22824afca7fc86d5f9c0b62cec66bfc" } } ], "extra": [ 1, 179, 74, 135, 85, 131, 47, 210, 146, 191, 62, 253, 69, 223, 222, 43, 170, 135, 216, 24, 24, 74, 26, 211, 38, 254, 138, 239, 208, 45, 0, 93, 84, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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