Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f232af876be30706585a7ebc69fb33a6f8164d43ba662f4d90c74cfe6e066f

Tx prefix hash: bfcbd215e1933eca6dd053b0adb3793f221e4b21dbf04b3882af16ff4c1cb311
Tx public key: 92e599fabaef692b252f513aecdd3663d8f2fd518890f042d9b651e78f599b95
Timestamp: 1577170233 Timestamp [UCT]: 2019-12-24 06:50:33 Age [y:d:h:m:s]: 05:072:05:22:38
Block: 30460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201484 RingCT/type: yes/0
Extra: 0192e599fabaef692b252f513aecdd3663d8f2fd518890f042d9b651e78f599b950211000000048a2ee0d9000000000000000000

1 output(s) for total of 486.498737862000 dcy

stealth address amount amount idx
00: e5e8155a9cc3c17b1214fd7bbc5c78006c15794d3ab0d7912e6bea34d4fbcf8a 486.498737862000 50296 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": 30470, "vin": [ { "gen": { "height": 30460 } } ], "vout": [ { "amount": 486498737862, "target": { "key": "e5e8155a9cc3c17b1214fd7bbc5c78006c15794d3ab0d7912e6bea34d4fbcf8a" } } ], "extra": [ 1, 146, 229, 153, 250, 186, 239, 105, 43, 37, 47, 81, 58, 236, 221, 54, 99, 216, 242, 253, 81, 136, 144, 240, 66, 217, 182, 81, 231, 143, 89, 155, 149, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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