Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472bc177f0beaec50be9aa6486c441d026fd8573d4f574e3ac4d6934a9f5a3b1

Tx prefix hash: a17589f1c2bc994cfb1a51029dbbedbb6c1ef80f9a624e08fbefe1beb7127f27
Tx public key: 9e9e6501be8b6ef0bbdbcd4b2b123e1b08d67fac03af0b543d7eb6ed27f7ac96
Timestamp: 1691348832 Timestamp [UCT]: 2023-08-06 19:07:12 Age [y:d:h:m:s]: 01:296:00:57:24
Block: 820279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472708 RingCT/type: yes/0
Extra: 019e9e6501be8b6ef0bbdbcd4b2b123e1b08d67fac03af0b543d7eb6ed27f7ac9602110000000a75e3f0e9000000000000000000

1 output(s) for total of 1.175101171000 dcy

stealth address amount amount idx
00: 78915848f48042242b336a39a39d3616bbee3fb33e3669a1fe13b8831e3c6dd4 1.175101171000 1272355 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": 820289, "vin": [ { "gen": { "height": 820279 } } ], "vout": [ { "amount": 1175101171, "target": { "key": "78915848f48042242b336a39a39d3616bbee3fb33e3669a1fe13b8831e3c6dd4" } } ], "extra": [ 1, 158, 158, 101, 1, 190, 139, 110, 240, 187, 219, 205, 75, 43, 18, 62, 27, 8, 214, 127, 172, 3, 175, 11, 84, 61, 126, 182, 237, 39, 247, 172, 150, 2, 17, 0, 0, 0, 10, 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