Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 371e18036279f2afe72ad71097e9248c145693b3962b2024949d9af0a5464744

Tx prefix hash: b80739eebe783591b3af1c56e32edecc20951d08ef4109593ca1d9dd61615f38
Tx public key: 2d9b298e03ee4948d8cee65f1819b04421829c25eae3bf9ff6e7031790d2ccfb
Timestamp: 1700919810 Timestamp [UCT]: 2023-11-25 13:43:30 Age [y:d:h:m:s]: 01:145:07:39:39
Block: 899377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365037 RingCT/type: yes/0
Extra: 012d9b298e03ee4948d8cee65f1819b04421829c25eae3bf9ff6e7031790d2ccfb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.642673857000 dcy

stealth address amount amount idx
00: 71ffe83cf447e6d505f647eb135ce06f488df70d867f62d6876b82a9d6df51c0 0.642673857000 1355830 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": 899387, "vin": [ { "gen": { "height": 899377 } } ], "vout": [ { "amount": 642673857, "target": { "key": "71ffe83cf447e6d505f647eb135ce06f488df70d867f62d6876b82a9d6df51c0" } } ], "extra": [ 1, 45, 155, 41, 142, 3, 238, 73, 72, 216, 206, 230, 95, 24, 25, 176, 68, 33, 130, 156, 37, 234, 227, 191, 159, 246, 231, 3, 23, 144, 210, 204, 251, 2, 17, 0, 0, 0, 4, 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