Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01e07fbd2136e2d3a97c6b0341871aa8decb889d9a849cba849c39b3e3a1126d

Tx prefix hash: a697c5623833cf50f80977e96ef42c569a422e03d11047c0182da0195b594944
Tx public key: 806e26d6c25e9fe01b3629b2cc08f5c0cab10d4402126fb54e0b4e8b5b98c154
Timestamp: 1706057878 Timestamp [UCT]: 2024-01-24 00:57:58 Age [y:d:h:m:s]: 01:091:10:56:52
Block: 941939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326480 RingCT/type: yes/0
Extra: 01806e26d6c25e9fe01b3629b2cc08f5c0cab10d4402126fb54e0b4e8b5b98c1540211000000600011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd44e9a8fef268341ba8f6176ad558f54c1ccb20361b503e9014142a380f7e71 0.600000000000 1400099 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": 941949, "vin": [ { "gen": { "height": 941939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd44e9a8fef268341ba8f6176ad558f54c1ccb20361b503e9014142a380f7e71" } } ], "extra": [ 1, 128, 110, 38, 214, 194, 94, 159, 224, 27, 54, 41, 178, 204, 8, 245, 192, 202, 177, 13, 68, 2, 18, 111, 181, 78, 11, 78, 139, 91, 152, 193, 84, 2, 17, 0, 0, 0, 96, 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