Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2610a4d01058fc860137e000736444a92873a50ffdf6f9c4dabd97c1112476e

Tx prefix hash: 51a69e24fc5f055fc1e5a5413b6daba115e8d36224a50ceee69db69eb235427e
Tx public key: 87801ba09caf82248d4be456c65f91e3bc222c1c40bb3d8ad1675e03d709e387
Timestamp: 1581306110 Timestamp [UCT]: 2020-02-10 03:41:50 Age [y:d:h:m:s]: 04:235:06:19:34
Block: 61746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1060289 RingCT/type: yes/0
Extra: 0187801ba09caf82248d4be456c65f91e3bc222c1c40bb3d8ad1675e03d709e3870211000000318a2ee0d9000000000000000000

1 output(s) for total of 383.193528536000 dcy

stealth address amount amount idx
00: 5ea541a84bed1d7ab04a3e90a036fbb5f3be82eb426c2a5ef371d2aff4a3930c 383.193528536000 113861 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": 61756, "vin": [ { "gen": { "height": 61746 } } ], "vout": [ { "amount": 383193528536, "target": { "key": "5ea541a84bed1d7ab04a3e90a036fbb5f3be82eb426c2a5ef371d2aff4a3930c" } } ], "extra": [ 1, 135, 128, 27, 160, 156, 175, 130, 36, 141, 75, 228, 86, 198, 95, 145, 227, 188, 34, 44, 28, 64, 187, 61, 138, 209, 103, 94, 3, 215, 9, 227, 135, 2, 17, 0, 0, 0, 49, 138, 46, 224, 217, 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