Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1d45ea739cfbe54b4afafbc11737baac96855cc5c7cbfd743e9fd618bb951b

Tx prefix hash: e73ce823dc7672c86d394d0da0be7edcd5b924a297c774a089a2beb725708acf
Tx public key: d4789e358ae7c62d14c152e586d38fbdb2a7e90aa0a8d516f7b8a2beb2a401f2
Timestamp: 1697565113 Timestamp [UCT]: 2023-10-17 17:51:53 Age [y:d:h:m:s]: 01:106:14:43:12
Block: 871756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337188 RingCT/type: yes/0
Extra: 01d4789e358ae7c62d14c152e586d38fbdb2a7e90aa0a8d516f7b8a2beb2a401f202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.793433464000 dcy

stealth address amount amount idx
00: 506046befa32f54a487314ab50c9e63328f1824c2810c178404bed957507345e 0.793433464000 1326781 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": 871766, "vin": [ { "gen": { "height": 871756 } } ], "vout": [ { "amount": 793433464, "target": { "key": "506046befa32f54a487314ab50c9e63328f1824c2810c178404bed957507345e" } } ], "extra": [ 1, 212, 120, 158, 53, 138, 231, 198, 45, 20, 193, 82, 229, 134, 211, 143, 189, 178, 167, 233, 10, 160, 168, 213, 22, 247, 184, 162, 190, 178, 164, 1, 242, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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