Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2ff2848db1a107db17e9cd937089b2f42a39fc5315a6ea4c52d8f3f86ec5e8

Tx prefix hash: 7f189985835676ef13ea28eaf6274060786996b3301ec7c92d6f7ca333d0e58b
Tx public key: 6fb22cc3e2aa3184c101c92ddf027c2824e76da429c69adf4d35f30ecabfabac
Timestamp: 1706359376 Timestamp [UCT]: 2024-01-27 12:42:56 Age [y:d:h:m:s]: 01:029:23:49:49
Block: 944448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282486 RingCT/type: yes/0
Extra: 016fb22cc3e2aa3184c101c92ddf027c2824e76da429c69adf4d35f30ecabfabac0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48aa18b6cf81905230ca6312b9cf85eb5f3094d9776e3e1e40c12d7c7971e8d0 0.600000000000 1402686 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": 944458, "vin": [ { "gen": { "height": 944448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48aa18b6cf81905230ca6312b9cf85eb5f3094d9776e3e1e40c12d7c7971e8d0" } } ], "extra": [ 1, 111, 178, 44, 195, 226, 170, 49, 132, 193, 1, 201, 45, 223, 2, 124, 40, 36, 231, 109, 164, 41, 198, 154, 223, 77, 53, 243, 14, 202, 191, 171, 172, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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