Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a60fc8cffa35813c497b672061ef5b9bcf16b53e92cdfa7c44cc7d8f0cc7f1

Tx prefix hash: e6451c0cec94f6de7f30b8dc660955b8c9af6552dcfc9beee6d96b651a034483
Tx public key: 32828f0342590a32fdd8161f24a09ce039a8f47b9da4c011f2c31d5869509b6a
Timestamp: 1755738541 Timestamp [UCT]: 2025-08-21 01:09:01 Age [y:d:h:m:s]: 00:140:07:21:10
Block: 1350954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100259 RingCT/type: yes/0
Extra: 0132828f0342590a32fdd8161f24a09ce039a8f47b9da4c011f2c31d5869509b6a021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a86f22e03e2efc3f1404ab7172b02fc8a9bd4530dbde2dfe60ceb685453eaa 0.600000000000 1838901 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": 1350964, "vin": [ { "gen": { "height": 1350954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a86f22e03e2efc3f1404ab7172b02fc8a9bd4530dbde2dfe60ceb685453eaa" } } ], "extra": [ 1, 50, 130, 143, 3, 66, 89, 10, 50, 253, 216, 22, 31, 36, 160, 156, 224, 57, 168, 244, 123, 157, 164, 192, 17, 242, 195, 29, 88, 105, 80, 155, 106, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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