Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a1db931007f7dd9f4ac8f4414efe23e2c0a3717c74c56aab91ec74c2c68620

Tx prefix hash: 0f99d6a279a7a274cda5bff443f84190008c94072598452a89289914e6c04683
Tx public key: ff97482124e1ab319bd2eaeda47297c64e80c0fa6d9c886574fd389c40deb10d
Timestamp: 1631561442 Timestamp [UCT]: 2021-09-13 19:30:42 Age [y:d:h:m:s]: 03:229:18:14:30
Block: 333121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 939639 RingCT/type: yes/0
Extra: 01ff97482124e1ab319bd2eaeda47297c64e80c0fa6d9c886574fd389c40deb10d021100000008f60c5d7e000000000000000000

1 output(s) for total of 48.331723677000 dcy

stealth address amount amount idx
00: fa4046928a222a5f8c394021108e87bb6f9549ce64a12e5e4e82b8f18ae5a7ea 48.331723677000 687566 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": 333131, "vin": [ { "gen": { "height": 333121 } } ], "vout": [ { "amount": 48331723677, "target": { "key": "fa4046928a222a5f8c394021108e87bb6f9549ce64a12e5e4e82b8f18ae5a7ea" } } ], "extra": [ 1, 255, 151, 72, 33, 36, 225, 171, 49, 155, 210, 234, 237, 164, 114, 151, 198, 78, 128, 192, 250, 109, 156, 136, 101, 116, 253, 56, 156, 64, 222, 177, 13, 2, 17, 0, 0, 0, 8, 246, 12, 93, 126, 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