Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f7ec84a9058c7aee6e1e435cc50863f9c3b7a9b80ce3753f06667ec8e3268e

Tx prefix hash: 5c3c90fa136b9b67237f2a3808a703bcc765c64b67de15bf9cb029938daec590
Tx public key: 2ecec40bfcf42a88cb8267e209fb41e453de6fc6fd03865a4f3a4354377dc716
Timestamp: 1681612913 Timestamp [UCT]: 2023-04-16 02:41:53 Age [y:d:h:m:s]: 01:272:08:10:33
Block: 739549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456146 RingCT/type: yes/0
Extra: 012ecec40bfcf42a88cb8267e209fb41e453de6fc6fd03865a4f3a4354377dc7160211000000015029cbac000000000000000000

1 output(s) for total of 2.175541539000 dcy

stealth address amount amount idx
00: ec8851d521c9f827c994a0cfa2c1c227036ffbd1e16c51bc333f369fb140aeab 2.175541539000 1186404 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": 739559, "vin": [ { "gen": { "height": 739549 } } ], "vout": [ { "amount": 2175541539, "target": { "key": "ec8851d521c9f827c994a0cfa2c1c227036ffbd1e16c51bc333f369fb140aeab" } } ], "extra": [ 1, 46, 206, 196, 11, 252, 244, 42, 136, 203, 130, 103, 226, 9, 251, 65, 228, 83, 222, 111, 198, 253, 3, 134, 90, 79, 58, 67, 84, 55, 125, 199, 22, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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