Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cd357670b5d32a09d2652c74af60dcd315c031c47b61b6716b36632dd362782

Tx prefix hash: eaa7d297327a2f9655250c1211b12bc9a21fd8d2ad802e0cb4bfaec88e175061
Tx public key: 788cf2f88a9960214d17fd11a388021116e77e7e17759054c2bc0d6f2afd6a31
Timestamp: 1746370736 Timestamp [UCT]: 2025-05-04 14:58:56 Age [y:d:h:m:s]: 00:200:13:29:08
Block: 1275652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141048 RingCT/type: yes/0
Extra: 01788cf2f88a9960214d17fd11a388021116e77e7e17759054c2bc0d6f2afd6a310211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 025ae8719283a2d1d66ba0b60d03440ae1faf7fc602e218c4d62e50c41cf9519 0.600000000000 1762967 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": 1275662, "vin": [ { "gen": { "height": 1275652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "025ae8719283a2d1d66ba0b60d03440ae1faf7fc602e218c4d62e50c41cf9519" } } ], "extra": [ 1, 120, 140, 242, 248, 138, 153, 96, 33, 77, 23, 253, 17, 163, 136, 2, 17, 22, 231, 126, 126, 23, 117, 144, 84, 194, 188, 13, 111, 42, 253, 106, 49, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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