Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f3f681748f196802deb165506620c416d852b5ed54d4d800b36494f00c7e2b5

Tx prefix hash: 5f7dc9ab1c737f91b5b7376df786030581fd5702126b8da8a15c75c9b597c3ee
Tx public key: 13339ce5795d39e7af7cf9445e6da5e48020b2b735d669b1d2c31fba39fc2048
Timestamp: 1766041746 Timestamp [UCT]: 2025-12-18 07:09:06 Age [y:d:h:m:s]: 00:003:03:01:52
Block: 1436131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2231 RingCT/type: yes/0
Extra: 0113339ce5795d39e7af7cf9445e6da5e48020b2b735d669b1d2c31fba39fc2048021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15740660c36da5c6249127e3f3d856080f4e4fd74d6c3e8246114a9097aa0d80 0.600000000000 1924936 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": 1436141, "vin": [ { "gen": { "height": 1436131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15740660c36da5c6249127e3f3d856080f4e4fd74d6c3e8246114a9097aa0d80" } } ], "extra": [ 1, 19, 51, 156, 229, 121, 93, 57, 231, 175, 124, 249, 68, 94, 109, 165, 228, 128, 32, 178, 183, 53, 214, 105, 177, 210, 195, 31, 186, 57, 252, 32, 72, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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