Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee04afea4dd80619456c58d6faaa8b4b5cbde20f325e129ad1e9a51cc32b0dad

Tx prefix hash: 4b2a57f978931995616941cbb8c4806690f3ffcef83fb6e074de0bf8b35b652c
Tx public key: c3555294325935251471f41f0f1ce39a3325e8959b5f639b73b214199dbd089e
Timestamp: 1737874820 Timestamp [UCT]: 2025-01-26 07:00:20 Age [y:d:h:m:s]: 01:004:06:30:20
Block: 1205547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261379 RingCT/type: yes/0
Extra: 01c3555294325935251471f41f0f1ce39a3325e8959b5f639b73b214199dbd089e021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8ef6e085e17120b333c0c1d8aa34fd57b5851989ce1d2eaad031ca6478f82f4 0.600000000000 1692244 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": 1205557, "vin": [ { "gen": { "height": 1205547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8ef6e085e17120b333c0c1d8aa34fd57b5851989ce1d2eaad031ca6478f82f4" } } ], "extra": [ 1, 195, 85, 82, 148, 50, 89, 53, 37, 20, 113, 244, 31, 15, 28, 227, 154, 51, 37, 232, 149, 155, 95, 99, 155, 115, 178, 20, 25, 157, 189, 8, 158, 2, 17, 0, 0, 0, 9, 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