Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec72ab792f89d1a14c405fecbf0905c4bc7a86ac36d364ac0e1622dc362e327d

Tx prefix hash: 5d4231d9e88cc06833afe27c2cc4252da3c4fd277f91a1fa9bbf2b575d175fef
Tx public key: 3ce7358ac90018003b19a65e9e7c0b851b3d2fd243b2126fa9023a02633a502f
Timestamp: 1726559402 Timestamp [UCT]: 2024-09-17 07:50:02 Age [y:d:h:m:s]: 00:181:03:41:30
Block: 1111934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129314 RingCT/type: yes/0
Extra: 013ce7358ac90018003b19a65e9e7c0b851b3d2fd243b2126fa9023a02633a502f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770c7f5ce508b65bbf5f081f25c975fe4c9791f83dd10ec3f96bb66b3f94dacb 0.600000000000 1591071 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": 1111944, "vin": [ { "gen": { "height": 1111934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770c7f5ce508b65bbf5f081f25c975fe4c9791f83dd10ec3f96bb66b3f94dacb" } } ], "extra": [ 1, 60, 231, 53, 138, 201, 0, 24, 0, 59, 25, 166, 94, 158, 124, 11, 133, 27, 61, 47, 210, 67, 178, 18, 111, 169, 2, 58, 2, 99, 58, 80, 47, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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