Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf2b41131f1695feccde6fda25ec0ba55f729c95378575d4bbc630fffb630023

Tx prefix hash: 797652eb49da1fd88b3622e6bab19a9187773831ba7547c35609cd082a456843
Tx public key: f62cfdc425276fe0c7adc3c346cc35cc9f477e76efa53e46080049a7cd841a05
Timestamp: 1686390375 Timestamp [UCT]: 2023-06-10 09:46:15 Age [y:d:h:m:s]: 02:157:03:57:02
Block: 779172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 632091 RingCT/type: yes/0
Extra: 01f62cfdc425276fe0c7adc3c346cc35cc9f477e76efa53e46080049a7cd841a0502110000000575e3f0e9000000000000000000

1 output(s) for total of 1.607977157000 dcy

stealth address amount amount idx
00: 0f5443d72ecdb1e1aaac7a491046f065b4b29c10c57f0c281f95f919b4442dd5 1.607977157000 1228817 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": 779182, "vin": [ { "gen": { "height": 779172 } } ], "vout": [ { "amount": 1607977157, "target": { "key": "0f5443d72ecdb1e1aaac7a491046f065b4b29c10c57f0c281f95f919b4442dd5" } } ], "extra": [ 1, 246, 44, 253, 196, 37, 39, 111, 224, 199, 173, 195, 195, 70, 204, 53, 204, 159, 71, 126, 118, 239, 165, 62, 70, 8, 0, 73, 167, 205, 132, 26, 5, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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