Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441e6fe18bdc4289c567aceb9717fd9d19fddc2f777318bb884b4ef15a2b62bd

Tx prefix hash: 4f21fdb8167ba6819ae0d1d79f0a545f825f200a5c55bf7ae87615d300664b46
Tx public key: 2d7b43091ea4eb51b61ffa528600f1fa3e7c66ba350d7aa84b26bb2d741890dd
Timestamp: 1698384258 Timestamp [UCT]: 2023-10-27 05:24:18 Age [y:d:h:m:s]: 01:086:11:37:56
Block: 878564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322982 RingCT/type: yes/0
Extra: 012d7b43091ea4eb51b61ffa528600f1fa3e7c66ba350d7aa84b26bb2d741890dd0211000000034b8f5122000000000000000000

1 output(s) for total of 0.753273646000 dcy

stealth address amount amount idx
00: a1dfc78a14068edb7db47f6b0b37d01da5e9764b626aca4fc23283da2d52c719 0.753273646000 1334016 of 0

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": 878574, "vin": [ { "gen": { "height": 878564 } } ], "vout": [ { "amount": 753273646, "target": { "key": "a1dfc78a14068edb7db47f6b0b37d01da5e9764b626aca4fc23283da2d52c719" } } ], "extra": [ 1, 45, 123, 67, 9, 30, 164, 235, 81, 182, 31, 250, 82, 134, 0, 241, 250, 62, 124, 102, 186, 53, 13, 122, 168, 75, 38, 187, 45, 116, 24, 144, 221, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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