Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23a6f056e8a41542190dcc67b416297102b6c480d6de6369eead14a18c1976b

Tx prefix hash: a7e3e391698e7dcb0a050939c4826e6469f4f9bc9c975646d7ba239569fa9b8a
Tx public key: 9207f3b2a6eb362e01dc80f1b53bfe4552b203d38187d48f4a58b6ddeed397a6
Timestamp: 1720821454 Timestamp [UCT]: 2024-07-12 21:57:34 Age [y:d:h:m:s]: 00:259:10:26:52
Block: 1064381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185328 RingCT/type: yes/0
Extra: 019207f3b2a6eb362e01dc80f1b53bfe4552b203d38187d48f4a58b6ddeed397a602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a6e3357df0d217ec9d7f41b8302f4f1521dbe4f2a7fd89b38f284b64dc9d48c 0.600000000000 1534906 of 15

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": 1064391, "vin": [ { "gen": { "height": 1064381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a6e3357df0d217ec9d7f41b8302f4f1521dbe4f2a7fd89b38f284b64dc9d48c" } } ], "extra": [ 1, 146, 7, 243, 178, 166, 235, 54, 46, 1, 220, 128, 241, 181, 59, 254, 69, 82, 178, 3, 211, 129, 135, 212, 143, 74, 88, 182, 221, 238, 211, 151, 166, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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