Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76835ec83744901ac74d8d3eb83c8a00b31904bd14c272c1d7bc00f691e4139d

Tx prefix hash: 630722cb39e0ec090777b00c2d40408cff6d5512075e8731f42f161e06fb2088
Tx public key: bf4c9889a3ead74ee6fb7bf675f2c4b7c6712903d4c89f7c88d265ae199a17ae
Timestamp: 1754749525 Timestamp [UCT]: 2025-08-09 14:25:25 Age [y:d:h:m:s]: 00:014:05:12:01
Block: 1343533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9370 RingCT/type: yes/0
Extra: 01bf4c9889a3ead74ee6fb7bf675f2c4b7c6712903d4c89f7c88d265ae199a17ae021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1838543a3fa1159c94f1b8680294bcc6917b33ec6eca2d08768c692cf44b16 0.600000000000 1831374 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": 1343543, "vin": [ { "gen": { "height": 1343533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1838543a3fa1159c94f1b8680294bcc6917b33ec6eca2d08768c692cf44b16" } } ], "extra": [ 1, 191, 76, 152, 137, 163, 234, 215, 78, 230, 251, 123, 246, 117, 242, 196, 183, 198, 113, 41, 3, 212, 200, 159, 124, 136, 210, 101, 174, 25, 154, 23, 174, 2, 17, 0, 0, 0, 3, 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