Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e9dbd0289eef3293dd4d4fc98052c8cc1c13f749326eebef4ced40dc57f98fa

Tx prefix hash: 534339e802f117ef9534dcbb410a83bdf94c9ca5dd842ec0d9a91c50d04ffaf6
Tx public key: 570617cbda7ac01e0fb7ba3f0a4be3ccbf756f69c5af36366068064be5af7aa9
Timestamp: 1705474039 Timestamp [UCT]: 2024-01-17 06:47:19 Age [y:d:h:m:s]: 01:152:04:49:15
Block: 937100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369832 RingCT/type: yes/0
Extra: 01570617cbda7ac01e0fb7ba3f0a4be3ccbf756f69c5af36366068064be5af7aa902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0bcca3586b0b1b385f0dcebe0c045ae006cd7ab82f8021ff4729e6f47d3eae 0.600000000000 1395144 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": 937110, "vin": [ { "gen": { "height": 937100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0bcca3586b0b1b385f0dcebe0c045ae006cd7ab82f8021ff4729e6f47d3eae" } } ], "extra": [ 1, 87, 6, 23, 203, 218, 122, 192, 30, 15, 183, 186, 63, 10, 75, 227, 204, 191, 117, 111, 105, 197, 175, 54, 54, 96, 104, 6, 75, 229, 175, 122, 169, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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