Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e240cf3f049f1bce91261d8e179849ab02b3f1095bf1d670ba0b981e8958dce

Tx prefix hash: b847414033cbc836daa7ef3c065afee112f1acc07e8c549afc253d9c0bd3de64
Tx public key: 14c3ef6ab7b8b5cc7132e717ee9a205b76a89b81b4461157029060099ba4db2f
Timestamp: 1732937463 Timestamp [UCT]: 2024-11-30 03:31:03 Age [y:d:h:m:s]: 00:124:03:58:23
Block: 1164719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88532 RingCT/type: yes/0
Extra: 0114c3ef6ab7b8b5cc7132e717ee9a205b76a89b81b4461157029060099ba4db2f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8db81d052e97b87795aa7d14ce51a1b7bf13714f72064dd3c6ec5f3fdf5c54c 0.600000000000 1650394 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": 1164729, "vin": [ { "gen": { "height": 1164719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8db81d052e97b87795aa7d14ce51a1b7bf13714f72064dd3c6ec5f3fdf5c54c" } } ], "extra": [ 1, 20, 195, 239, 106, 183, 184, 181, 204, 113, 50, 231, 23, 238, 154, 32, 91, 118, 168, 155, 129, 180, 70, 17, 87, 2, 144, 96, 9, 155, 164, 219, 47, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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