Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533479af122d3b08e459b72251c0188fb471adde13a8e4aa676f60746f91c2e6

Tx prefix hash: 6a49bd768c2a2989336e5e55af1e91121fbb63639de789066b1ba44e11d3c3ab
Tx public key: 0e5ca92dfad95b4f1a9f7eebb35cac38bff8628b37bc6f048413f20317b0ed07
Timestamp: 1727135403 Timestamp [UCT]: 2024-09-23 23:50:03 Age [y:d:h:m:s]: 00:198:03:47:47
Block: 1116709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141445 RingCT/type: yes/0
Extra: 010e5ca92dfad95b4f1a9f7eebb35cac38bff8628b37bc6f048413f20317b0ed07021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c7b799925f7fec532421e7cff25572bb4a7a2b6c80d45f55afc174b101ed5c 0.600000000000 1597290 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": 1116719, "vin": [ { "gen": { "height": 1116709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c7b799925f7fec532421e7cff25572bb4a7a2b6c80d45f55afc174b101ed5c" } } ], "extra": [ 1, 14, 92, 169, 45, 250, 217, 91, 79, 26, 159, 126, 235, 179, 92, 172, 56, 191, 248, 98, 139, 55, 188, 111, 4, 132, 19, 242, 3, 23, 176, 237, 7, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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