Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e13db8b9cb31eabe44bbf00eab786cace3f2f028b34b262007a7b3ecb1670eb

Tx prefix hash: cc6353a0236bc5a57e73ddfe629a03df905ef6957fc67801d57f942f99176547
Tx public key: 9aeb39fa295824d1d3137fa202648002fdc3eeb2f81f4e86eb720b2beb478403
Timestamp: 1632169584 Timestamp [UCT]: 2021-09-20 20:26:24 Age [y:d:h:m:s]: 03:135:08:21:19
Block: 337762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872499 RingCT/type: yes/0
Extra: 019aeb39fa295824d1d3137fa202648002fdc3eeb2f81f4e86eb720b2beb478403021100000021f29d7abf000000000000000000

1 output(s) for total of 46.650329731000 dcy

stealth address amount amount idx
00: 3477918c488e8c923ba93e33fa234b2435003efd3f6d8c6ba1cc096fd61c3a81 46.650329731000 695383 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": 337772, "vin": [ { "gen": { "height": 337762 } } ], "vout": [ { "amount": 46650329731, "target": { "key": "3477918c488e8c923ba93e33fa234b2435003efd3f6d8c6ba1cc096fd61c3a81" } } ], "extra": [ 1, 154, 235, 57, 250, 41, 88, 36, 209, 211, 19, 127, 162, 2, 100, 128, 2, 253, 195, 238, 178, 248, 31, 78, 134, 235, 114, 11, 43, 235, 71, 132, 3, 2, 17, 0, 0, 0, 33, 242, 157, 122, 191, 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