Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769b80a9617fc086ef6ab800267ab7173a23156bd917ef36d33d2c3b2dcdf0e1

Tx prefix hash: fa1b9fd9113fd8e06ac0362c533bc0214d86443738adff6d8442eb3b4cd717a8
Tx public key: 20a157f8574c8d23578530234aa782b06c650652f05416158e7ea80a28e93e4a
Timestamp: 1735249273 Timestamp [UCT]: 2024-12-26 21:41:13 Age [y:d:h:m:s]: 00:089:10:12:40
Block: 1183854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63679 RingCT/type: yes/0
Extra: 0120a157f8574c8d23578530234aa782b06c650652f05416158e7ea80a28e93e4a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7fcd9e2dc2324984f7bf60bb848ea35568c17f422a411dc8cec72e06e95659b 0.600000000000 1670303 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": 1183864, "vin": [ { "gen": { "height": 1183854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7fcd9e2dc2324984f7bf60bb848ea35568c17f422a411dc8cec72e06e95659b" } } ], "extra": [ 1, 32, 161, 87, 248, 87, 76, 141, 35, 87, 133, 48, 35, 74, 167, 130, 176, 108, 101, 6, 82, 240, 84, 22, 21, 142, 126, 168, 10, 40, 233, 62, 74, 2, 17, 0, 0, 0, 5, 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