Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f71f92a74916245fe6c22c89844f477d644ab613d069f7caefed6ba00bb9c6c

Tx prefix hash: f34f8123db35169334e0b41dbe9a18e62286913dd3ae9e75e1a78333b4e9ec9f
Tx public key: 1ff10e9c7a10d0dc071f4f5083fed7b4fe8a1195810291266292e062c7679e79
Timestamp: 1707512415 Timestamp [UCT]: 2024-02-09 21:00:15 Age [y:d:h:m:s]: 01:075:12:23:28
Block: 954020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315035 RingCT/type: yes/0
Extra: 011ff10e9c7a10d0dc071f4f5083fed7b4fe8a1195810291266292e062c7679e7902110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a48e85147a06b4000aaa97c793dc6939db120a75b8bfa64dac2e721427d8d7a4 0.600000000000 1413292 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": 954030, "vin": [ { "gen": { "height": 954020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a48e85147a06b4000aaa97c793dc6939db120a75b8bfa64dac2e721427d8d7a4" } } ], "extra": [ 1, 31, 241, 14, 156, 122, 16, 208, 220, 7, 31, 79, 80, 131, 254, 215, 180, 254, 138, 17, 149, 129, 2, 145, 38, 98, 146, 224, 98, 199, 103, 158, 121, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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