Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e2f10a84330769cf1b785ef65c06f25d197c2d90b3d30035bbf013c25b10d4

Tx prefix hash: f3b8bcc508907bdedac0d78bf78fabe9fa35902df70c37ed877d498cbf63f21f
Tx public key: f239d63da5973feef77e17b40fb807f11b141fc83a9640e7a3bbd7ab52a9ab7a
Timestamp: 1736884175 Timestamp [UCT]: 2025-01-14 19:49:35 Age [y:d:h:m:s]: 00:183:03:20:27
Block: 1197380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129638 RingCT/type: yes/0
Extra: 01f239d63da5973feef77e17b40fb807f11b141fc83a9640e7a3bbd7ab52a9ab7a02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ce62b00f2cffc9e2b3a1cac7a62f00e6feca5095c5ce6a3680b5f000cdd1085 0.600000000000 1683987 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": 1197390, "vin": [ { "gen": { "height": 1197380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ce62b00f2cffc9e2b3a1cac7a62f00e6feca5095c5ce6a3680b5f000cdd1085" } } ], "extra": [ 1, 242, 57, 214, 61, 165, 151, 63, 238, 247, 126, 23, 180, 15, 184, 7, 241, 27, 20, 31, 200, 58, 150, 64, 231, 163, 187, 215, 171, 82, 169, 171, 122, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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