Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5030ba99782495768026a82e6b32d8fbd915c1d8a965ead72445b8586c725321

Tx prefix hash: 86fcf84a22a5ab9d7fc88db45425f7b859147db920fd99fbffb1538a8b3c791e
Tx public key: dcddb0092cf154d8ae3183e6d354d48a1b9ffe77f43c0b39dd3aa5a59d85fec0
Timestamp: 1738357550 Timestamp [UCT]: 2025-01-31 21:05:50 Age [y:d:h:m:s]: 00:293:17:57:36
Block: 1209319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207701 RingCT/type: yes/0
Extra: 01dcddb0092cf154d8ae3183e6d354d48a1b9ffe77f43c0b39dd3aa5a59d85fec0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68356eb8ac658820f5f3687f42017b3a83c29d514dcd9cdda6c8222267b34e4 0.600000000000 1696060 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": 1209329, "vin": [ { "gen": { "height": 1209319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68356eb8ac658820f5f3687f42017b3a83c29d514dcd9cdda6c8222267b34e4" } } ], "extra": [ 1, 220, 221, 176, 9, 44, 241, 84, 216, 174, 49, 131, 230, 211, 84, 212, 138, 27, 159, 254, 119, 244, 60, 11, 57, 221, 58, 165, 165, 157, 133, 254, 192, 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