Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 577f4308e0f72291de99a9f1ad77502bdcdebd1cbbcd86917a2cb211c907672f

Tx prefix hash: 4d445b9204a5bd2ad29e1932326283d895ca5f65c0f420dae1ccdc311f2cfc33
Tx public key: 4b4e60b9d344cfc4b3e65071c2b0cf09db2aa69a47ca235926ab64d5ff8b142d
Timestamp: 1739849834 Timestamp [UCT]: 2025-02-18 03:37:14 Age [y:d:h:m:s]: 00:343:08:37:52
Block: 1221639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243099 RingCT/type: yes/0
Extra: 014b4e60b9d344cfc4b3e65071c2b0cf09db2aa69a47ca235926ab64d5ff8b142d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f2f2b2d29e4c4c459c3499e8390e52f48aa4470a0577b1f08aaf70e4e5bda9 0.600000000000 1708484 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": 1221649, "vin": [ { "gen": { "height": 1221639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f2f2b2d29e4c4c459c3499e8390e52f48aa4470a0577b1f08aaf70e4e5bda9" } } ], "extra": [ 1, 75, 78, 96, 185, 211, 68, 207, 196, 179, 230, 80, 113, 194, 176, 207, 9, 219, 42, 166, 154, 71, 202, 35, 89, 38, 171, 100, 213, 255, 139, 20, 45, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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