Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1f69b66ef77d5187569defa9025aca1b2491f8536a7a3d533472b702a7c9a1

Tx prefix hash: da5b64dc15a890d442abeb84a7342ec52b70e30eef1f47c204d6cb492919dd78
Tx public key: e44d101f0a572a5f8ce53e9f95519c704a7c5f9c93da2cb546fabb81159b25c2
Timestamp: 1725540261 Timestamp [UCT]: 2024-09-05 12:44:21 Age [y:d:h:m:s]: 01:064:03:20:58
Block: 1103491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304265 RingCT/type: yes/0
Extra: 01e44d101f0a572a5f8ce53e9f95519c704a7c5f9c93da2cb546fabb81159b25c202110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61978056a975bf8118e8d76bbed356b409fe6ab3e4b76f65b5691a3aaac73d18 0.600000000000 1580340 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": 1103501, "vin": [ { "gen": { "height": 1103491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61978056a975bf8118e8d76bbed356b409fe6ab3e4b76f65b5691a3aaac73d18" } } ], "extra": [ 1, 228, 77, 16, 31, 10, 87, 42, 95, 140, 229, 62, 159, 149, 81, 156, 112, 74, 124, 95, 156, 147, 218, 44, 181, 70, 250, 187, 129, 21, 155, 37, 194, 2, 17, 0, 0, 0, 19, 145, 225, 60, 4, 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