Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74d96cfabc397997d7e68ddb6ed37a0a41fae3ad309f6ab4bf83fff86ca1fee

Tx prefix hash: dc65879c4071245c0eb4db773bf3825385d66146702599253ae8c373dbb47398
Tx public key: 5fdd8a434cba84451cf0b3a55627626e4f77e30cf39d2d714336e704c2031a4c
Timestamp: 1718891462 Timestamp [UCT]: 2024-06-20 13:51:02 Age [y:d:h:m:s]: 01:153:22:10:53
Block: 1048367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368567 RingCT/type: yes/0
Extra: 015fdd8a434cba84451cf0b3a55627626e4f77e30cf39d2d714336e704c2031a4c02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 996b070c1048a0e48e2f75b6e2d48febe496d4baccf255c8d12d9e7dce650d7f 0.600000000000 1518436 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": 1048377, "vin": [ { "gen": { "height": 1048367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "996b070c1048a0e48e2f75b6e2d48febe496d4baccf255c8d12d9e7dce650d7f" } } ], "extra": [ 1, 95, 221, 138, 67, 76, 186, 132, 69, 28, 240, 179, 165, 86, 39, 98, 110, 79, 119, 227, 12, 243, 157, 45, 113, 67, 54, 231, 4, 194, 3, 26, 76, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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