Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e71819ea3cc7a73aa35fefa622af86001424ecf12e4d0cf68052f1e8e13d0069

Tx prefix hash: 727fc8dd941bd83715f9452a00e5958b22c5ffcc0816088e5a211cd84f47b51f
Tx public key: 442fa3846be8cb0c33e6cf666e54e9b1c0481d3c2e23a01ebf9640a6d985048f
Timestamp: 1716153254 Timestamp [UCT]: 2024-05-19 21:14:14 Age [y:d:h:m:s]: 00:356:21:39:50
Block: 1025665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255112 RingCT/type: yes/0
Extra: 01442fa3846be8cb0c33e6cf666e54e9b1c0481d3c2e23a01ebf9640a6d985048f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3374f1984089b1e2addcfc75bbc4f695d341526593e400886556b59d6c50627d 0.600000000000 1492328 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": 1025675, "vin": [ { "gen": { "height": 1025665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3374f1984089b1e2addcfc75bbc4f695d341526593e400886556b59d6c50627d" } } ], "extra": [ 1, 68, 47, 163, 132, 107, 232, 203, 12, 51, 230, 207, 102, 110, 84, 233, 177, 192, 72, 29, 60, 46, 35, 160, 30, 191, 150, 64, 166, 217, 133, 4, 143, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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