Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616f3efb0c5ba4818bcc7a3f640aee94444daf7cc7ef5bf22a407266616f1919

Tx prefix hash: 24d9b7ebedb70599a37a75f359fd7fb60f8edf15754902270be0f0c820ddf0cb
Tx public key: 7048e9048df04a021cb06ecc3d0143e7f2ca9cf1f127594e89ca5193eaef4418
Timestamp: 1729871606 Timestamp [UCT]: 2024-10-25 15:53:26 Age [y:d:h:m:s]: 01:051:20:24:58
Block: 1139357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295493 RingCT/type: yes/0
Extra: 017048e9048df04a021cb06ecc3d0143e7f2ca9cf1f127594e89ca5193eaef4418021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4851c25ff635d8a1f303e29879cd9eb63b9159ef242a29ea4e73cf3cb953ab1a 0.600000000000 1623144 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": 1139367, "vin": [ { "gen": { "height": 1139357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4851c25ff635d8a1f303e29879cd9eb63b9159ef242a29ea4e73cf3cb953ab1a" } } ], "extra": [ 1, 112, 72, 233, 4, 141, 240, 74, 2, 28, 176, 110, 204, 61, 1, 67, 231, 242, 202, 156, 241, 241, 39, 89, 78, 137, 202, 81, 147, 234, 239, 68, 24, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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