Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dde3ef516780cce98d537e2d02582803e8bb8565b0e4e82054699a0726055b

Tx prefix hash: e5d4af9531a810bb8e3724eb8b8b485654b5a72ef3e70aec57611b9e71322749
Tx public key: 4c2c28e002eea9fdc775cb91db447a235a5e1d18d617df1a2de82fc567c15c7b
Timestamp: 1648280777 Timestamp [UCT]: 2022-03-26 07:46:17 Age [y:d:h:m:s]: 03:061:03:40:28
Block: 466652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 823931 RingCT/type: yes/0
Extra: 014c2c28e002eea9fdc775cb91db447a235a5e1d18d617df1a2de82fc567c15c7b02110000000c4a0f5013000000000000000000

1 output(s) for total of 17.449719972000 dcy

stealth address amount amount idx
00: 652ac220711d1751625b5cbf5a5ba80a1f1ad3efe7375f4be91dc94a351b2c50 17.449719972000 885007 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": 466662, "vin": [ { "gen": { "height": 466652 } } ], "vout": [ { "amount": 17449719972, "target": { "key": "652ac220711d1751625b5cbf5a5ba80a1f1ad3efe7375f4be91dc94a351b2c50" } } ], "extra": [ 1, 76, 44, 40, 224, 2, 238, 169, 253, 199, 117, 203, 145, 219, 68, 122, 35, 90, 94, 29, 24, 214, 23, 223, 26, 45, 232, 47, 197, 103, 193, 92, 123, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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