Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b27b25d06ff1c9d8d5bf99687df96e8a6ec34a6f750b1f68a3adddb385717020

Tx prefix hash: 8265136e3ae4a3732900cf31faf825fe4037fa1bbcc86dcb7bc492e0cacb1fec
Tx public key: bd8207964e57e2954560c3012413aa6da0b95864fb42d31f0e1e300ff920b80f
Timestamp: 1764485452 Timestamp [UCT]: 2025-11-30 06:50:52 Age [y:d:h:m:s]: 00:038:05:22:06
Block: 1423231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27376 RingCT/type: yes/0
Extra: 01bd8207964e57e2954560c3012413aa6da0b95864fb42d31f0e1e300ff920b80f021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7496d1ea425a2b76ef14737261d1b45861aa75b71ebeefa97ea1fac2c38464c 0.600000000000 1911834 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": 1423241, "vin": [ { "gen": { "height": 1423231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7496d1ea425a2b76ef14737261d1b45861aa75b71ebeefa97ea1fac2c38464c" } } ], "extra": [ 1, 189, 130, 7, 150, 78, 87, 226, 149, 69, 96, 195, 1, 36, 19, 170, 109, 160, 185, 88, 100, 251, 66, 211, 31, 14, 30, 48, 15, 249, 32, 184, 15, 2, 17, 0, 0, 0, 5, 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