Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d731b4187184345060850c886284f45e99b4067dddff0987625e3eb3500e54b5

Tx prefix hash: a675526540f05ccae0c5fbe539d0f173021ae7e0b69ef736412fd9d32ebb9c03
Tx public key: e935af05f4aa9f0f4aa2c7ee4d35e293ba50fc1890e28c018b9b4aec48cc052e
Timestamp: 1587144054 Timestamp [UCT]: 2020-04-17 17:20:54 Age [y:d:h:m:s]: 04:258:03:19:17
Block: 93698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092984 RingCT/type: yes/0
Extra: 01e935af05f4aa9f0f4aa2c7ee4d35e293ba50fc1890e28c018b9b4aec48cc052e02110000002160e3cc90000000000000000000

1 output(s) for total of 300.289675224000 dcy

stealth address amount amount idx
00: 771f874c789093df2200378e6f7ce414f6f291d2afb430729ba1ae2e1a18c0d7 300.289675224000 166772 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": 93708, "vin": [ { "gen": { "height": 93698 } } ], "vout": [ { "amount": 300289675224, "target": { "key": "771f874c789093df2200378e6f7ce414f6f291d2afb430729ba1ae2e1a18c0d7" } } ], "extra": [ 1, 233, 53, 175, 5, 244, 170, 159, 15, 74, 162, 199, 238, 77, 53, 226, 147, 186, 80, 252, 24, 144, 226, 140, 1, 139, 155, 74, 236, 72, 204, 5, 46, 2, 17, 0, 0, 0, 33, 96, 227, 204, 144, 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