Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f641968739041d770ee9f4d336411252f9e143686cec6aa05afec74104e4ca

Tx prefix hash: 3797d1d78acf9179280bdf0b1f81bad24443fb5fe681d54ae852848cb5c2522e
Tx public key: d9489f1d20cceb0d1a86c463628e45d3333720433b2626b1550e35fa0d9497ad
Timestamp: 1700127887 Timestamp [UCT]: 2023-11-16 09:44:47 Age [y:d:h:m:s]: 01:137:17:31:08
Block: 892813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359593 RingCT/type: yes/0
Extra: 01d9489f1d20cceb0d1a86c463628e45d3333720433b2626b1550e35fa0d9497ad02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.675738190000 dcy

stealth address amount amount idx
00: fc1b7a2fbb2e760777b6b10c413b1ec975f701d64c460b1dd8bfccc50ebfb681 0.675738190000 1348948 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": 892823, "vin": [ { "gen": { "height": 892813 } } ], "vout": [ { "amount": 675738190, "target": { "key": "fc1b7a2fbb2e760777b6b10c413b1ec975f701d64c460b1dd8bfccc50ebfb681" } } ], "extra": [ 1, 217, 72, 159, 29, 32, 204, 235, 13, 26, 134, 196, 99, 98, 142, 69, 211, 51, 55, 32, 67, 59, 38, 38, 177, 85, 14, 53, 250, 13, 148, 151, 173, 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