Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34920e8da997e1cd0e1e7e0a77fa5cbd3ea1948d095d207f31f353e1dc2b07d1

Tx prefix hash: 9b72e2ee6c67d74510cb000ef0b00ccfa67809afd1e956bc4b4667f2653846e1
Tx public key: f9d2010233d79cb9ce22b0f289e4d5de0b6933ad99ab72fd5eef008ea106bb91
Timestamp: 1734445734 Timestamp [UCT]: 2024-12-17 14:28:54 Age [y:d:h:m:s]: 00:178:10:20:38
Block: 1177229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127260 RingCT/type: yes/0
Extra: 01f9d2010233d79cb9ce22b0f289e4d5de0b6933ad99ab72fd5eef008ea106bb910211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35fe86363fb35d015a7b843013895bfd0a1df7553a3727e5d03ba14be0524ed1 0.600000000000 1663594 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": 1177239, "vin": [ { "gen": { "height": 1177229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35fe86363fb35d015a7b843013895bfd0a1df7553a3727e5d03ba14be0524ed1" } } ], "extra": [ 1, 249, 210, 1, 2, 51, 215, 156, 185, 206, 34, 176, 242, 137, 228, 213, 222, 11, 105, 51, 173, 153, 171, 114, 253, 94, 239, 0, 142, 161, 6, 187, 145, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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