Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7170be5c5839c0478e8c37954c9a0920eb6e8b62a8aca17847c2f9c2614a52dc

Tx prefix hash: 894964b2d092b531664136afd37c44d51410bbecd7e6a4de33a74e274d946dd2
Tx public key: 3b5c18d6864c159da637171616dd5f83722df0cb7bcb667a19837a8d7e8cd014
Timestamp: 1722085462 Timestamp [UCT]: 2024-07-27 13:04:22 Age [y:d:h:m:s]: 00:120:15:26:57
Block: 1074845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86312 RingCT/type: yes/0
Extra: 013b5c18d6864c159da637171616dd5f83722df0cb7bcb667a19837a8d7e8cd014021100000030e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f2a01a41b81f97f7c69c0a36c05052d56ec6430b59880ff348e37b3718bed0 0.600000000000 1547364 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": 1074855, "vin": [ { "gen": { "height": 1074845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f2a01a41b81f97f7c69c0a36c05052d56ec6430b59880ff348e37b3718bed0" } } ], "extra": [ 1, 59, 92, 24, 214, 134, 76, 21, 157, 166, 55, 23, 22, 22, 221, 95, 131, 114, 45, 240, 203, 123, 203, 102, 122, 25, 131, 122, 141, 126, 140, 208, 20, 2, 17, 0, 0, 0, 48, 233, 20, 221, 21, 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