Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10c316d719b84f62413c1524ff28a34b8e437c3d4254e06c3fbb0271c711f707

Tx prefix hash: 68aaf5df878de9863846618bfeaaca761a8f2d092406f29508bbc08a8a76cd2e
Tx public key: 5f14fa0f935f5af6445e2aa4f85db80d71e34ef24a11bfb66fac4013260adbf0
Timestamp: 1715480511 Timestamp [UCT]: 2024-05-12 02:21:51 Age [y:d:h:m:s]: 01:185:22:19:02
Block: 1020124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391468 RingCT/type: yes/0
Extra: 015f14fa0f935f5af6445e2aa4f85db80d71e34ef24a11bfb66fac4013260adbf002110000000641ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c69ba2768f3e569b0f7c0633041dcb147b270ec1b55aa46407f3f73daa0bf391 0.600000000000 1484183 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": 1020134, "vin": [ { "gen": { "height": 1020124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c69ba2768f3e569b0f7c0633041dcb147b270ec1b55aa46407f3f73daa0bf391" } } ], "extra": [ 1, 95, 20, 250, 15, 147, 95, 90, 246, 68, 94, 42, 164, 248, 93, 184, 13, 113, 227, 78, 242, 74, 17, 191, 182, 111, 172, 64, 19, 38, 10, 219, 240, 2, 17, 0, 0, 0, 6, 65, 238, 28, 155, 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